home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.19970929-19971216 / 000037_news@newsmaster….columbia.edu _Fri Oct 3 03:13:42 1997.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB

  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id DAA07525
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Fri, 3 Oct 1997 03:13:41 -0400 (EDT)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id DAA29178
  7.     for kermit.misc@watsun; Fri, 3 Oct 1997 03:13:41 -0400 (EDT)
  8. Path: news.columbia.edu!sol.ctr.columbia.edu!spool.mu.edu!uwm.edu!gsl-penn-ns.gsl.net!news.gsl.net!gip.net!sunqbc.risq.qc.ca!news.bc.net!rover.ucs.ualberta.ca!alberta!not-for-mail
  9. From: Vladimir Alexiev <vladimir@cs.ualberta.ca>
  10. Newsgroups: comp.protocols.kermit.misc
  11. Subject: Re: Kermit via PPP under DOS?
  12. Date: 29 Sep 1997 13:57:10 -0600
  13. Organization: University of Alberta, Computing Science
  14. Lines: 12
  15. Message-ID: <om90wf99m1.fsf@tees.cs.ualberta.ca>
  16. References: <60i3al$8l@gateway.dircsa.org.au>
  17.     <60km6a$jsb@gateway.dircsa.org.au>
  18. NNTP-Posting-Host: tees.cs.ualberta.ca
  19. In-reply-to: arthur@gateway.dircsa.org.au's message of 28 Sep 1997 13:54:42 +0930
  20. X-Newsreader: Gnus v5.0.15
  21. Xref: news.columbia.edu comp.protocols.kermit.misc:7804
  22.  
  23. In article <60km6a$jsb@gateway.dircsa.org.au> arthur@gateway.dircsa.org.au (Arthur Marsh) writes:
  24.  
  25. > "check tcp" only determines whether support is compiled in.
  26. > I did the following in my MSCUSTOM.INI to have a single configuration for 
  27. > both serial and IP connections:
  28. > set port tcp/ip <ip-address>
  29. > if success forward passedserial
  30.  
  31. I think that this will always succeed, because the actual connection is only
  32. attempted when CONNECT is issued. You should check "if success" after CONNECT,
  33. and if it's failed eventually examine \v(tcpip_status).